Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1357

reference
311-tree-1
name
1357
tree-preservation-order

undefined

311-tpo-1
uprn
address-text
point
POINT (-1.026531 50.893272)
geometry
MULTIPOLYGON (((-1.026460 50.893264,-1.026463 50.893278,-1.026473 50.893291,-1.026488 50.893301,-1.026508 50.893308,-1.026530 50.893310,-1.026552 50.893308,-1.026572 50.893302,-1.026588 50.893292,-1.026598 50.893279,-1.026602 50.893266,-1.026599 50.893252,-1.026589 50.893239,-1.026574 50.893229,-1.026554 50.893222,-1.026532 50.893220,-1.026510 50.893222,-1.026490 50.893228,-1.026474 50.893238,-1.026464 50.893250,-1.026460 50.893264)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL